-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moved metadata_store into database and content_discovery #7773
Conversation
47ca1d1
to
d582312
Compare
d582312
to
39d5db7
Compare
db_path = ":memory:" | ||
|
||
self.db = TriblerDatabase(str(db_path)) | ||
|
||
# TODO: merge the code below into the TriblerDatabase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a TODO for the next PR, or is it a forgotten TODO for the current PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for the next PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of the developers and I in this group consider it bad, or let's say "not good," practice to merge changes with TODOs into the main branch.
I'm not stopping you from doing this by not giving acceptance to the PR. I'm just highlighting that there are many points of view on this practice, some of which consider it to be a bad practice that leads to code quality degradation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with them. However, our current linters are configured to allow this. Notably, I did not have to disable any warnings to pass our PR checks.
Once we fix #1722 we can adopt a more strict stance on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you saying that if you understand there is a bad practice, but there are no configured linter issues, then it is okay for you to commit and merge the code despite its quality?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though I disagree with the practice personally, this is the approach that the team has chosen and I adapt my workflow to it.
If I were the only developer, I would make make own standards and conform to what I would like to see. Sadly, I am not the only developer and I have to conform to the existing rules and linter settings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Related to #7669, following the plan of #7669 (comment)
The changes of this PR are simply moves and dead code removal.
Unit tests have been added to cover missing lines (in our existing code). The lines in
database_component.py
that are part ofgui_test_mode
orchant_testnet
are not covered.